-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Add EIP: Precompile for ML-DSA signature verification #10557
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Merge ethereum eips
File
|
ae12e2b to
b34675e
Compare
EIPS/eip-dilithium.md
Outdated
| @@ -0,0 +1,261 @@ | |||
| --- | |||
| eip: 9999 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| eip: 9999 | |
| eip: 8051 |
Assigning next sequential EIP/ERC/RIP number.
Numbers are assigned by editors & associates.
Please also update the filename.
EIPS/eip-8051.md
Outdated
| title: Precompile for ML-DSA signature verification | ||
| description: Proposal to add precompiled contracts that perform signature verifications using the NIST-standard FIPS-204 ML-DSA and an EVM-friendly variant | ||
| author: Renaud Dubois (@rdubois-crypto), Simon Masson (@simonmasson) | ||
| discussions-to: https://ethereum-magicians.org/t/add-eip-ml-dsa-verification/25857 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| discussions-to: https://ethereum-magicians.org/t/add-eip-ml-dsa-verification/25857 | |
| discussions-to: https://ethereum-magicians.org/t/eip-8051-ml-dsa-verification/25857 |
Updated with assigned number
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the discussions topic to use the template
https://ethereum-magicians.org/c/eips/5
|
The commit 1de80f2 (as a parent of fecd5a9) contains errors. |
|
|
||
| ## Reference Implementation | ||
|
|
||
| An implementation is provided in `assets` of this EIP. For the NIST-compliant version, KAT vectors of the NIST submission are valid. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SamWilsn how best to handle reference implementation, again we have code attached in assets. How can we let people refer to full working code implementations?
@simonmasson instead of having full code attached, we prefer if you showcase the implementation through high level concepts/pseudo code instead of trying to attach a full working code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at bls12 eip, which face similar problems, would test vectors be enough ?
This proposal creates a two contracts for:
This enables post-quantum secure signatures for Ethereum.